Skip to content

UPSTREAM: <carry>: support feature gate filtering from upstream #2310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

stbenjam
Copy link
Member

@stbenjam stbenjam commented May 21, 2025

When considering upstream feature gates, not all are known or present in
openshift/api, so we have to be selective about which we filter on.

This uses data provided by OTE and an allow list to include/exclude
upstream tests.

$ k8s-tests-ext list tests --platform aws --feature-gate VolumeAttributesClass |
jq '.[].name' | grep VolumeAttributesClass | wc -l
30
$ k8s-tests-ext list tests --platform aws |
jq '.[].name' | grep VolumeAttributesClass | wc -l
0

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label May 21, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 21, 2025
Copy link

openshift-ci bot commented May 21, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label May 21, 2025
Copy link

openshift-ci bot commented May 21, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: stbenjam
Once this PR has been reviewed and has the lgtm label, please assign benluddy for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview origin/pull#29837

Copy link

openshift-ci bot commented May 21, 2025

@stbenjam: An error was encountered. No known errors were detected, please see the full error message for details.

Full error message. unable to get pr from github for: origin/pull#29837: Get "http://ghproxy/repos/origin/pull/pulls/29837": failed to get installation id for org origin: the github app is not installed in organization origin

Please contact an administrator to resolve this issue.

@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn origin/pull#29837

Copy link

openshift-ci bot commented May 21, 2025

@stbenjam: An error was encountered. No known errors were detected, please see the full error message for details.

Full error message. unable to get pr from github for: origin/pull#29837: Get "http://ghproxy/repos/origin/pull/pulls/29837": failed to get installation id for org origin: the github app is not installed in organization origin

Please contact an administrator to resolve this issue.

@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn openshift/origin#29837

Copy link

openshift-ci bot commented May 21, 2025

@stbenjam: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a5238290-3665-11f0-9423-47e5a5f1b3c7-0

@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview openshift/origin#29837

Copy link

openshift-ci bot commented May 21, 2025

@stbenjam: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/a8b49890-3665-11f0-841c-bc234f3dfb38-0

@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial openshift/origin#29837

Copy link

openshift-ci bot commented May 22, 2025

@stbenjam: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/15120af0-370a-11f0-91e1-0a72cb4275f5-0

@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-serial openshift/origin#29837

Copy link

openshift-ci bot commented May 22, 2025

@stbenjam: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1d263810-370a-11f0-94bb-2354090009ae-0

@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial openshift/origin#29837

Copy link

openshift-ci bot commented May 28, 2025

@stbenjam: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/cfd5f2b0-3bc0-11f0-924b-46625cc1174a-0

@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-serial openshift/origin#29837

Copy link

openshift-ci bot commented May 28, 2025

@stbenjam: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d6c241a0-3bc0-11f0-9346-379432385884-0

@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

stbenjam added 2 commits May 29, 2025 10:04
When considering upstream feature gates, not all are known or present in
openshift/api, so we have to be selective about which we filter on.

This uses data provided by OTE and an allow list to include/exclude
upstream tests.

$ k8s-tests-ext list tests --platform aws --feature-gate VolumeAttributesClass |\
  jq '.[].name' | grep VolumeAttributesClass | wc -l
30
$ k8s-tests-ext list tests --platform aws |\
  jq '.[].name' | grep VolumeAttributesClass | wc -l
       0
@openshift-ci-robot
Copy link

@stbenjam: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@stbenjam
Copy link
Member Author

stbenjam commented May 29, 2025

Re-opening with a clean PR

@stbenjam stbenjam closed this May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants